Important: Unless otherwise specified, all information in this chapter applies to both Sun Solaris and Red Hat Enterprise Linux-based WEM systems.The .java.policy file is created on the WEM server and downloaded along with the applet.
In each case the entire grant statement has to be replaced before the file is inserted into the correct directory (see Placement of Required Client Files for more information).
Important: If a single desktop is used to manage multiple WEM servers, there can only be one .java.policy file on the desktop. This means the user needs to add a complete grant clause with the server’s IP address for each server under management. |
•
|
Java® Runtime Environment (JRE) - This program must be installed on the client workstation. Versions 1.5, and 1.6 are supported.
|
|
•
|
Java Policy File - This file may be obtained from the WEM server when you first access the system using the client workstation. For proper authentication, this policy file must be located in an exact location, dependent upon the operating system being used on the client workstation.
|
|
•
|
For the Microsoft® Windows™ NT 4.0 operating system, the .java.policy file must be placed in the <drive_letter>\Profiles\<user_name> directory.
|
|
•
|
For the Microsoft® Windows™ 2000 and Windows™ XP operating systems, the .java.policy file must be placed in the <drive_letter>\Documents and Settings\<user_name> directory.
|
|
•
|
For the Microsoft® Windows™ 7 operating system, the .java.policy file must be placed in the <drive_letter>\users\<user_name> directory.
|
|
•
|
For the Sun® Solaris® (UNIX) and Linux® operating systems, the .java.policy file must be placed in the user's home directory.
|
|
•
|
Instructions on how to download the Java Policy file from the WEM server are displayed when you click the Java Policy File link, located towards the right of the client application's WEM browser display.
|
setenv NPX_PLUGIN_PATH /<java_installation_directory>/jre/plugin/sparc/ns4
setenv NPX_JRE_PATH /<java_installation_directory>
<java_installation_directory> is the directory in which java is installed (i.e. /usr/java).
|
Step 2
|
Source the .cshrc file (or open a new shell) and start the Netscape browser.
|
|
Step 1
|
Set the following environment variables in your .profile file:
|
NPX_PLUGIN_PATH=/<java_installation_directory>/jre/plugin/sparc/ns4
NPX_JRE_PATH=/<java_installation_directory>
<java_installation_directory> is the directory in which java is installed (i.e. /usr/java).
|
Step 2
|
If these variables are set in a shell, then invoke Netscape from the same shell (e.g. /usr/dt/appconfig/netscape/netscape).
|
The <Web_Element_Manager_server_IP_address> variable is the IP address of the WEM server entered in dotted-decimal notation.
Important: After an upgrade or installing a new version of WEM, it is recommended that the browser cache of the client workstation should be cleared, if it is enabled. To clear the cache in Internet Explorer, click Tools menu -> Internet Options. Under the General tab, click Delete Files, click the Delete all offline content check box, and then click OK.The superuser account is the default administrative account on the WEM. This account works similar to the root account on a UNIX machine. A superuser administrator would have to create accounts for the individual users in the WEM - like a UNIX machine root user does. The user accounts would then be given to the non-superuser users. The superuser password should be kept private to limit access.
Important: The first time you log into the superuser account, you will be prompted to change your password. See ANSI T1.276 Compliance in the Web Element Manager Overview for more information about password usage.
The Management Toolbar, which can be enabled or disabled from the View menu, provides shortcuts to access various functions available via the Pull-down Menu. Shortcuts include:
 |
||
 |
||
 |
 Important: This operation only saves WEM application configuration items. It does not save any configuration text file operations that are made on a selected system. |
|
 |
 Important: This icon is only available when audio alarms are enabled through the Alarm Management pull-down menu. |
|
 |
 Important: This icon is only available when audio alarms are enabled through the Alarm Management pull-down menu. |
|
 |
 Important: The audible alarm function described here has no effect on audible alarms generated by the chassis itself, through its SMC and SPIO cards. This function is only applicable to the WEM client; and is configurable on a per chassis basis. |
|
 |
||
 |
Menu options available to users can be hidden and unhidden at will by setting a flag in the menu.xml file. Setting the flag appropriately is described in the WEM Configuration File Parameters appendix.
The File pull-down menu option allows users to either log out of a current session, save any configuration changes, or exit the WEM application completely.
The Client pull-down allows users to control and customize how the management application and selected devices are viewed on their browser-based client. These settings are configured on a per-user basis. Additionally, this menu provides options for launching other tools that can be used for management purposes such as Telnet and/or Secure Shell (SSH) clients and Management Information Base (MIB) browsers.
The System Info pull-down menu allows you to view system-level information for devices selected in the topology window. From this menu, you also can perform some configuration and system administration operations.
The Alarm Management pull-down menu allows users to manage current, pending, and outstanding events as well as view statistics for alarms. This menu also provides controls for configuring the system Central Office (CO) alarm indicators and audio indicators.
The Configuration pull-down menu allows administrators to perform various configuration options upon a selected system. This includes system-level parameters such as those for hardware as well as all context-level parameters such as services, interfaces, and protocols. Also included in this menu are the options for specifying the systems to be managed by the WEM.
The Performance pull-down menu allows users to view, configure, modify, collect, and view real-time statistical information for a selected device.
The Monitor/Test menu offers selections that enable the user to view and configure parameters to monitor and test selected functions such as:
|
•
|
EMS Process Monitoring: This option allows you to view system and disk usage, and interface information about the WEM server application. You can also configure various threshold settings that will create an alarm when the system exceeds your configured thresholds.
|
|
•
|
Monitor Protocol: This option enables a powerful monitoring tool that can be configured to collect and display specific protocol information for calls coming into or out of the selected system. This powerful tool can be used to help troubleshoot session or connectivity problems.
|
|
•
|
Monitor Subscriber: This option provides the same powerful monitoring options as explained above, but can be used for a specific subscriber.
|
|
•
|
Port Monitoring This option allows the users to view, enable/disable the process, and configure the parameter thresholds and intervals for line cards and ports.
|
The Test option allows users to perform tests such as RADIUS server connectivity, PPP echo tests, or AAA packet transmit and receive.
The Security pull-down menu provides administrative users with user management functions such as adding and deleting administrative users, monitoring user sessions, and viewing audit trail information.
General help is accessed through the Help pull-down menu, located at the top of the menu bar. Click Contents to access the main Help screen. It is important to note that context-sensitive help is available for each dialog that possesses a Help button. More information on using the online help is available in the Obtaining Help within the WEM section later in this chapter.
New topology maps can be added by using the Add function, available from the Map pull-down menu. Network devices can be added to an existing topographical map by using the Modify function, available from the Map pull-down menu.
This area provides system messages from the WEM application to the user. These messages notify the user as to what the application is currently doing. For example, when a user selects a new device from the Topographical Map or Object Tree, the system sends a message to the user that it is attempting to “Attempting to Fetch Contexts” for the selected device.
|
•
|
Green: Indicates that a communications link between the WEM server and the client is established and functioning in an idle state
|
|
•
|
Red: Indicating that the WEM server is busy or a communications problem may be present. During normal operations, the indicator may flash red momentarily, as this indicates that the server is obtaining information from its managed devices (e.g. obtaining a list of contexts from a device or group of devices when a user selects it from the map), but it should return to green in less than 30 seconds.
|
Important: This help file is a general purpose file. Accordingly, not all Product features/functionality described in this file are necessarily included in the particular Product version you may be using, or there may be features/functionality contained in a Product version that may not be included in this help file.General Help is accessed through the Help pull-down menu, located at the top of the menu bar. Click the Contents option from this menu to access the help system’s welcome screen.
|
•
|
Contents: The Contents tab provides a “table of contents” for the Help system. Like a printed book, subjects are organized into various sections. To open a particular section, click on the “+” sign to the left of the book icon for that section. When opened, each section will display the various Help topics associated with that section. When a user selects an option, such as a hyperlink or other option from a Help screen, the Contents section will automatically highlight the individual section and topic.
|
|
•
|
Index: The Index tab is exactly like the index in any document, in that it allows the user to view various entries in alphabetical order. The advantage of a web-based index is that the user may also use the Index function to search for all instances of indexed keywords. When a user enters a search word, the user is moved to the matching area of the index. If there is more than one link available for that indexed keyword, the system will display a pop-up window wherein the user can select the option they want to display.
|
|
•
|
Search: The Search tab allows the user to perform searches for a specific word or phrase across the entire Help system.
|
To remove the left-most frame from the display, click the Hide button, located at the upper right corner of the main window. To enable the frame, click the Show button. These buttons work as a toggle, wherein one or the other appears, as dictated by the status of the help system tab views.
Context-sensitive help is displayed when a user clicks the Help button displayed on an operations screen.
Offline help can be accessed or downloaded without logging in to the WEM GUI. Navigate to the WEM page using your browser and click the “Web Element Manager Offline Help” link under the Help Resources section to download the WEM help in .CHM file format.
